Skip to content

Conversation

katmayb
Copy link
Contributor

@katmayb katmayb commented Sep 25, 2025

This PR updates the docs for LangSmith Platform, folding in LGP. Specifically:

  • Update to tab arrangement.
  • Big content changes in Deployments tab (now Agent deployment as well as Platform infrastructure deployment).
  • Changing the name of the Studio feature.
  • Overhaul of home page.
  • Updates to tab landing pages to follow the same card format consistently.
  • Moving LGP content into the LS directory in the docs.

Latest preview:

https://langchain-5e9cc07a-preview-langsm-1760109143-df9b7ef.mintlify.app/langsmith/home

@github-actions github-actions bot added langsmith For docs changes to LangSmith langgraph-platform For docs changes to LangGraph Platform labels Sep 25, 2025
Copy link
Contributor

Preview ID generated: preview-langsm-1758824315-b51cbe2

Copy link
Contributor

Preview ID generated: preview-langsm-1759174519-2fcf987

Copy link
Contributor

Preview ID generated: preview-langsm-1759176996-f20be3d

@katmayb katmayb force-pushed the langsmith-platform branch from e8aab3b to 9c76609 Compare October 1, 2025 18:07
Copy link
Contributor

github-actions bot commented Oct 1, 2025

Preview ID generated: preview-langsm-1759342075-296f79d

@katmayb katmayb force-pushed the langsmith-platform branch 2 times, most recently from a7896cd to 1fa67c3 Compare October 1, 2025 20:51
Copy link
Contributor

github-actions bot commented Oct 1, 2025

Preview ID generated: preview-langsm-1759351956-78e92d8

@katmayb katmayb force-pushed the langsmith-platform branch from 1fa67c3 to 1c19df5 Compare October 2, 2025 17:22
@github-actions github-actions bot added langchain For docs changes to LangChain langgraph For docs changes to LangGraph oss javascript labels Oct 2, 2025
@katmayb katmayb force-pushed the langsmith-platform branch from 0c08343 to 6e19883 Compare October 2, 2025 20:51
Copy link
Contributor

github-actions bot commented Oct 2, 2025

Preview ID generated: preview-langsm-1759438309-4bf2e07

@katmayb katmayb force-pushed the langsmith-platform branch from 6e19883 to 67e123b Compare October 3, 2025 12:43
Copy link
Contributor

github-actions bot commented Oct 3, 2025

Preview ID generated: preview-langsm-1759495425-7827e03

@katmayb katmayb force-pushed the langsmith-platform branch from 67e123b to 4eb0e2b Compare October 3, 2025 13:41
@github-actions github-actions bot added python For content related to the Python version of LangChain projects labs labels Oct 3, 2025
Copy link
Contributor

github-actions bot commented Oct 3, 2025

Preview ID generated: preview-langsm-1759498954-167ce7c

Copy link
Contributor

github-actions bot commented Oct 3, 2025

Preview ID generated: preview-langsm-1759500119-896821e

@katmayb katmayb force-pushed the langsmith-platform branch from b2876e5 to 11305b3 Compare October 3, 2025 16:03
Copy link
Contributor

@andrewnguonly andrewnguonly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First, thanks for working on these changes, @katmayb. Here are my latest high-level thoughts that don't apply directly to any specific change in this PR, but is broadly relevant to the overall restructuring.

  1. I couldn't look at every change in the PR. It's too big.
  2. I understand that the primary goal of this PR is to accommodate the product renaming/consolidation and information restructuring. There are some places where I've commented on specific content changes, so feel free to ignore these comments if it's easier to address these in a separate PR.
  3. It might be nice to create some kind of informational banner/page that describes what changes have been made; a doc for the doc changes.
  4. Creating a new Hosting tab feels like the right direction. However, I think it's still challenging to understand that there are different "modules" within LangSmith and that there are different ways to enable/disable them. I will provide some suggestions/ideas for how we could make the content more clear outside of this PR. We may have to make these changes after the launch.


This section covers how to package, build, and deploy your _agents_ and applications.

_Deployment_ focuses on how to build and deploy your graphs (or agentic workflows) as [LangGraph Servers](/langsmith/langgraph-server).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since LangSmith Deployment literally only supports building and deploying LangGraph OSS graphs, I'd be fine with being more specific/precise here: Deployment focuses on how to build and deploy your LangGraph graphs as LangGraph Servers.

Not blocking.

Side bar: I'm really averse to using "agentic workflows" here because there's been so much discussion/controversy around naming and definitions of things (e.g. OpenAI Dev Day Agent Builder release, Harrison's follow-up blog post). Because of the quickly evolving nature of these things, my preference is that our documentation is dumb and simple and decoupled from this noise. For example, in 6 months, "agentic workflows" might mean something else and/or there will be a new term: "agentic work streams".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a good point. I removed this instance of "agentic workflows". It would be worthwhile to do a bit of a follow-up on this — I want the docs terminology to be as clear and relevant for as long as possible.

title: Run a LangGraph application locally
sidebarTitle: Run a LangGraph application locally
title: Run a LangGraph app locally
sidebarTitle: Run a LangGraph app locally
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: To be consistent with the new hosting.mdx page, LangGraph app --> LangGraph Server

title: Run a LangGraph Server locally
sidebarTitle: Run a LangGraph Server locally

There are other places where we use the term app, LangGraph app, and LangGraph application, and LangSmith application. For consistency, should we change all instances to LangGraph Server? I won't comment on all places in this PR. Also, this can probably be done as part of a different PR.

Side bar: I won't comment in all places, but we seem to be using LangGraph Server and LangSmith application interchangeably in the new docs. This is increasing the confusion IMHO. Can we only use 1 term?

Side, side bar: Do we need a Glossary of Terms page? This might be helpful.

src/docs.json Outdated
]
},
{
"group": "Platform components",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Platform components --> Deployment components

The items under this section are only for LangSmith Deployment. Platform feels too wide/vague (for now).

```

You can find your project & tenant IDs with a GET request to the `/info` endpoint on your LangGraph Platform deployment.
You can find your project & tenant IDs with a GET request to the `/info` endpoint on your LangSmith deployment.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit, but maybe disregard this comment: project & tenant IDs --> deployment (project_id) & workspace IDs (tenant_id)

A long time ago, we used to call deployments, "projects" and we used to call workspaces, "tenants". We never updated the GET /info endpoint. Source code:

async def meta_info(request: ApiRequest):
    plus = plus_features_enabled()
    return JSONResponse(
        {
            "version": __version__,
            "langgraph_py_version": langgraph.version.__version__,
            "flags": {
                "assistants": True,
                "crons": plus and config.FF_CRONS_ENABLED,
                "langsmith": bool(config.LANGSMITH_CONTROL_PLANE_API_KEY)
                and bool(config.TRACING),
                "langsmith_tracing_replicas": True,
            },
            "host": {
                "kind": metadata.HOST,
                "project_id": metadata.PROJECT_ID,
                "host_revision_id": metadata.HOST_REVISION_ID,
                "revision_id": metadata.REVISION,
                "tenant_id": metadata.TENANT_ID,
            },
        }
    )

@katmayb katmayb force-pushed the langsmith-platform branch from 89630f5 to 7592722 Compare October 14, 2025 13:08
Copy link
Contributor

Preview ID generated: preview-langsm-1760447342-72c9244

@katmayb katmayb marked this pull request as ready for review October 14, 2025 14:06
@katmayb katmayb force-pushed the langsmith-platform branch from 7592722 to 4293425 Compare October 14, 2025 14:07
Copy link
Contributor

Preview ID generated: preview-langsm-1760450868-be36abc

Copy link
Contributor

Preview ID generated: preview-langsm-1760451311-f04e2be

@katmayb katmayb merged commit 68a794b into main Oct 14, 2025
11 checks passed
@katmayb katmayb deleted the langsmith-platform branch October 14, 2025 14:21
mdrxy pushed a commit that referenced this pull request Oct 14, 2025
This PR updates the docs for LangSmith Platform, folding in LGP.
Specifically:

- Update to tab arrangement.
- Big content changes in Deployments tab (now Agent deployment as well
as Platform infrastructure deployment).
- Changing the name of the Studio feature.
- Overhaul of home page.
- Updates to tab landing pages to follow the same card format
consistently.
- Moving LGP content into the LS directory in the docs.

## Latest preview:


https://langchain-5e9cc07a-preview-langsm-1760109143-df9b7ef.mintlify.app/langsmith/home
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-infra labs langchain For docs changes to LangChain langgraph For docs changes to LangGraph langgraph-platform For docs changes to LangGraph Platform langsmith For docs changes to LangSmith oss python For content related to the Python version of LangChain projects

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants